Creates a Layer 2 VPN, which can be either a VPLS or VPWS.
| vpls_name | Identifies the VPLS within the switch (character string). The vpls_name string must begin with an alphabetic character, and may contain up to 31 additional alphanumeric characters. |
| vpws_name | Identifies the VPWS within the switch (character string). The vpws_name string must begin with an alphabetic character, and may contain up to 31 additional alphanumeric characters. |
| pwid | Specifies a PW ID. Must be a non-zero 32-bit value that has network-wide significance. |
For the VPLS dot1q tag, the default value is exclude.
Each VPLS or VPWS is a member of a single VPN, and each VPN can have only one associated VPLS or VPWS per switch. External to the switch, each VPN has an identifier.
A VPLS or VPWS name must begin with an alphabetical character and may contain alphanumeric characters and underscores (_), but it cannot contain spaces. The maximum allowed length for a name is 32 characters. For name creation guidelines and a list of reserved names, see Object Names in the Switch Engine v33.1.1 User Guide .
Any non-zero 32-bit value that has network-wide significance can be specified for the identifier. This pwid is used on all pseudo-wires in the VPLS.
The l2vpn keyword is introduced in ExtremeXOS Release 12.4 and is required when creating a VPWS. For backward compatibility, the l2vpn keyword is optional when creating a VPLS. However, this keyword will be required in a future release, so we recommend that you use this keyword for new configurations and scripts.
Note
The switch's LSR ID must be configured before a VPLS or VPWS can be created.This example creates a VPLS with 99 as the PW ID:
create vpls vpls1 fec-id-type pseudo-wire 99
The following example creates a VPWS with 101 as the PW ID:
create l2vpn vpws vpws1 fec-id-type pseudo-wire 101
This command was first available in ExtremeXOS 11.6.
The l2vpn and vpws keywords were first available in ExtremeXOS 12.4.
This command is available only on the platforms that support MPLS as described in the Switch Engine v33.1.1 Licensing Guide document.